Message-ID: <20559727.1075854297094.JavaMail.evans@thyme>
Date: Fri, 23 Mar 2001 06:30:00 -0800 (PST)
From: matt.pena@enron.com
To: daren.farmer@enron.com
Subject: RE: What happened: tempdb xact log
Cc: chris.schomer@enron.com, jaikishore.bharathi@enron.com, bob.ward@enron.com, 
	william.mallary@enron.com, brian.ripley@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ANSI_X3.4-1968
Content-Transfer-Encoding: quoted-printable
Bcc: chris.schomer@enron.com, jaikishore.bharathi@enron.com, bob.ward@enron.com, 
	william.mallary@enron.com, brian.ripley@enron.com
X-From: Matt Pena
X-To: Daren J Farmer
X-cc: Chris Schomer, Jaikishore Bharathi, Bob Ward, William Mallary, Brian Ripley
X-bcc: 
X-Folder: \Darren_Farmer_Jun2001\Notes Folders\Discussion threads
X-Origin: Farmer-D
X-FileName: dfarmer.nsf

Darren,
Do you know if you were running pulling up the Path Manager for a date rang=
e=20
around 10:51?=01; How do you normally pull up the Path Manager?=01; Please =
let me=20
know as we're attempting to find out what caused this problem and if we=20
should restrict access on the date range functionality.=01; If you were onl=
y=20
pulling it for a day, that would be okay.
=01;
Thanks

-----Original Message-----
From: Mallary, William=20
Sent: Friday, March 23, 2001 2:24 PM
To: Ripley, Brian
Cc: Schomer, Chris; Pena, Matt; Bharathi, Jaikishore; Ward, Bob
Subject: What happened: tempdb xact log


Brian,=20
=01;
At 11:20am this morning, a stored procedure (source_dest_list_range_sp, Lin=
e=20
#172) being run by Daren Farmer caused the tempdb transaction log on=20
unifygasp to fill up.=01; This procedure is run routinely by many other use=
rs on=20
a daily basis without incident.=01; At the time of the failure, this stored=
=20
procedure had been running since 10:51am, or roughly 30 minutes.=01; I was=
=20
notified via automatic page at 11:24am; the page indicating that there was=
=20
200MB free.=01; I immediately checked tempdb, which was by full by this tim=
e.=01;=20
Three attempts to clear the transaction log prior to 11:30am finally result=
ed=20
in=01;a cleared transaction log.
=01;
Kishore noiced shortly thereafter that there was a problem in the way that=
=20
Sybase was accounting for its free space, a condition which may have been=
=20
crucial to the failure since nearly 5GB of space was apparently unavailable=
=20
to the transaction log.=01; A reboot of unifyprod2 at 1:40pm cleared this=
=20
condition.

Bill Mallary
*=01; william.mallary@enron.com <mailto:william.mallary@enron.com>
( =01;713.345.3485 (office)
( =01;281.960.7181 (cell)

=01;